(maint) Clear Azure source directory on builds #1776
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Occasionally files intended to live in containers get written on Windows with the wrong line endings. Linux containers need LF line endings for executable scripts and config files (for instance), but the default checkout on Windows is CRLF, unless explicitly configured to be different. Unfortunately a subsequent pull of the code will not reset local line endings on Windows, even when .gitattributes is set properly. This typically results in RDPing into an Azure DevOps builder and manually trashing the source code, so that when the code is next checked out, the appropriate LF line endings will be set. Instead of doing that, have the `s` (source) subdirectory purged on each build. https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#job
|
CLA signed by all contributors. |
|
Azure passed, but the check never came back to GH for some reason... hmmph. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Occasionally files intended to live in containers get written on
Windows with the wrong line endings. Linux containers need LF line
endings for executable scripts and config files (for instance), but
the default checkout on Windows is CRLF, unless explicitly configured
to be different.
Unfortunately a subsequent pull of the code will not reset local
line endings on Windows, even when .gitattributes is set properly.
This typically results in RDPing into an Azure DevOps builder and
manually trashing the source code, so that when the code is next
checked out, the appropriate LF line endings will be set.
Instead of doing that, have the
s(source) subdirectory purgedon each build.
https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#job